Ue identifier in rrc resume

ABSTRACT

Systems and methods relating to resuming a suspended connection of a wireless device in a wireless system are disclosed. In some embodiments, a method of operation of a wireless device comprises receiving ( 100 ), from a first network node, a first message that instructs the wireless device to suspend a connection between the wireless device and the wireless system. The method further comprises, upon an occurrence of a triggering event, transmitting ( 108 ), to a second network node, a second message that requests that the connection. The second message comprises a resume identifier that comprises a part that identifies the first network node and a part that identifies the wireless device. The method further comprises receiving ( 116 ), from the second network node, a third message that indicates that the connection between the wireless device and the wireless system is being resumed.

RELATED APPLICATIONS

This application claims the benefit of provisional patent applicationSer. No. 62/256,378, filed Nov. 17, 2015, the disclosure of which ishereby incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to a Radio Resource Control (RRC) resumeprocedure in a cellular communications network.

BACKGROUND

Cellular communication systems are currently being developed andimproved for Machine Type Communication (MTC), communicationcharacterized by lower demands on data rates than for example mobilebroadband, but with higher requirements on, e.g., low cost devicedesign, better coverage, and ability to operate for years on batterieswithout charging or replacing the batteries. One of the maincharacteristics of MTC is infrequent transmission of small amounts ofdata. It is expected that the number of MTC devices will increaseexponentially but the data size per device will remain small. In ThirdGeneration Partnership Project (3GPP) Long Term Evolution (LTE), thecurrent data transfer procedures are not optimized for small datatransfers and short lived sessions, which results in a large signalingoverhead.

To handle small data transfers more efficiently, 3GPP has studiedmethods to reduce the signaling overhead when transitioning from RadioResource Control (RRC) IDLE to RRC CONNECTED. One of the chosensolutions is “RRC resume,” which is based on re-using the User Equipment(UE) context from the previous RRC connection for the subsequent RRCconnection setup. By storing the UE context in the enhanced or evolvedNode B (eNB), one can avoid the signaling required for securityactivation and bearer establishment at the next RRC IDLE to RRCCONNECTED transition. Although the term “UE” is used throughout thisdocument, “Wireless Device” or “WD” may be used interchangeably. It willbe understood that the UEs/WDs as described herein are not limited tomobile phones, but may extend to any fixed or mobile device with awireless connection that performs MTC. Likewise, although the term “eNB”is used herein, “eNB” or “base station” may be used interchangeably andmay more generally be referred to as types of radio access nodes.

RRC resume is realized by introducing two new procedures: RRC Suspendand RRC Resume. The eNB suspends a connection by sending a RRCConnection Suspend (also referred to herein as an RRC Connection Suspendmessage) to the UE. This may happen, for example, after the UE has beeninactive for a certain period of time, as shown in FIG. 1. Note that, in3GPP Release 13, RRC Connection Suspend is signaled with anRRCConnectionRelease message with releaseCause set to “rrc-Suspend.”Both the UE and eNB store the UE context and an associated identifier(ID), which is referred to herein as Resume ID. The UE context contains,e.g., bearer configuration and security related parameters. In 3GPPRelease 13, the RRC Connection Suspend message contains the Resume ID,but does not contain security parameters. However, in future releases,in addition to the Resume ID, it may be possible for the RRC ConnectionSuspend message to also contain security related parameters (Next hopChaining Counter (NCC) and integrity and ciphering algorithms) which arerequired when Access Stratum (AS) security is later re-established.

At the next transition from RRC IDLE to RRC CONNECTED, the UE resumesthe connection by sending a RRC Connection Resume Request (also referredto herein as a RRC Connection Resume Request message) to the eNB, asshown in FIG. 2. The RRC Connection Resume Request message contains thepreviously received Resume ID, which the eNB uses to retrieve the UEcontext. An authorization token is also provided to allow the eNB tosecurely identify the UE. The authorization token may also be referredto as an authentication token. Assuming that the UE context is found andthe authorization token is valid, the eNB responds with a RRC ConnectionResume (also referred to herein as a RRC Connection Resume message) toconfirm that the connection is being resumed. The UE acknowledges thereception by sending a RRC Connection Resume Complete (also referred toherein as a RRC Connection Resume Complete message).

Note that the messages RRC Connection Suspend, RRC Connection ResumeRequest, RRC Connection Resume, and RRC Connection Resume Completeshould be seen as placeholders that describe their functionality; theirnames may differ in the final specification of RRC resume.

RRC resume is not necessarily limited to a single cell or single eNB,but can also be supported across eNBs. Inter-eNB connection resumptionis handled using context fetching, whereby the resuming eNB retrievesthe UE context from the suspending eNB over the X2 interface. Theresuming eNB provides the Resume ID, which is used by the suspending eNBto identify the UE context.

One problem that arises with RRC resume supporting inter-eNB connectionresumption is that the resuming eNB must retrieve the UE context fromthe suspending eNB. Thus, there is a need for systems and methods thatenable the resuming eNB to quickly and efficiently identify thesuspending eNB such that the UE context can be retrieved.

SUMMARY

Systems and methods relating to resuming a suspended connection of awireless device in a wireless system are disclosed. In some embodiments,a method of operation of a wireless device in a wireless systemcomprises receiving, from a first network node, a first message thatinstructs the wireless device to suspend a connection between thewireless device and the wireless system where, upon receiving the firstmessage, the wireless device stores a wireless device context of thewireless device and enters a suspended mode of operation. The methodfurther comprises, upon an occurrence of a triggering event,transmitting, to a second network node, a second message that requeststhat the connection between the wireless device and the wireless systembe resumed. The second message comprises a resume identifier, and theresume identifier comprises a part that identifies the first networknode to which the wireless device was connected upon suspending theconnection and a part that identifies the wireless device. The methodfurther comprises receiving, from the second network node, a thirdmessage that indicates that the connection between the wireless deviceand the wireless system is being resumed using the stored wirelessdevice context of the wireless device. The use of the resume identifierthat includes the part that identifies the first network node and thepart that identifies the wireless device enables the second network nodeto obtain the context of the wireless device from the first networknode. This is particularly beneficial in scenarios in which the firstand second network nodes are different network nodes.

In some embodiments, the wireless system is a Long Term Evolution (LTE)network, the part of the resume identifier that identifies the firstnetwork node is an Evolved Universal Terrestrial Radio Access Network(E-UTRAN) Cell Identifier (ID) (ECI), and the part of the resumeidentifier that identifies the wireless device is a Cell Radio NetworkTemporary ID (C-RNTI).

In some embodiments, an ordering of the parts within the resumeidentifier is such that the part of the resume identifier thatidentifies the first network node occurs first in the ordering and thepart of the resume identifier that identifies the wireless device occursafter the part of the resume identifier that identifies the firstnetwork node in the ordering. In some other embodiments, an ordering ofthe parts within the resume identifier is such that the part of theresume identifier that identifies the wireless device occurs first inthe ordering and the part of the resume identifier that identifies thefirst network node occurs after the part of the resume identifier thatidentifies the wireless device in the ordering.

In some embodiments, the resume identifier further comprises a part thatcontains a group identifier assigned to the wireless device. Further, insome embodiments, an ordering of the parts within the resume identifieris such that the part of the resume identifier that identifies thewireless device occurs first in the ordering, the part that contains thegroup identifier assigned to the wireless device occurs after the partof the resume identifier that identifies the wireless device in theordering, and the part of the resume identifier that identifies thefirst network node occurs after the part that contains the groupidentifier assigned to the wireless device in the ordering. Further, insome embodiments, bit orders within the parts of the resume identifierare reversed.

In some embodiments, the third message that indicates that theconnection between the wireless device and the wireless system is beingresumed comprises a copy of the second message that requests that theconnection between the wireless device and the wireless system beresumed.

In some embodiments, a Medium Access Control (MAC) control elementassociated with the third message comprises a copy of the second messagethat requests that the connection between the wireless device and thewireless system be resumed.

In some embodiments, a MAC control element associated with the thirdmessage comprises a copy of a portion of the second message thatrequests that the connection between the wireless device and thewireless system be resumed. Further, in some embodiments, the portion ofthe second message comprises the part of the resume identifier thatidentifies the wireless device. In some embodiments, the second messagefurther comprises an authorization token that allows the second networknode to securely identify the wireless device, and the portion of thesecond message comprises the authorization token. In some embodiments,the resume identifier further comprises a part that contains a groupidentifier assigned to the wireless device, and the portion of thesecond message comprises the part of the resume identifier that containsthe group identifier. In some embodiments, the second message istransmitted in an uplink common control channel service data unit, andthe portion of the second message is provided by truncating the uplinkcommon control channel service data unit. In some embodiments, thesecond message is transmitted in an uplink common control channelservice data unit, and the portion of the second message is provided bytruncating the uplink common control channel service data unit to a sizeof an existing content resolution identity MAC control element in LTE.In some embodiments, the second message is transmitted in an uplinkcommon control channel service data unit, and the portion of the secondmessage is provided by truncating the uplink common control channelservice data unit to 48 bits.

In some embodiments, the wireless device context comprises a bearerconfiguration of the wireless device and security related parameters.

In some embodiments, the first network node and the second network nodeare different network nodes. In some other embodiments, the firstnetwork node and the second network node are the same network node.

Embodiments of a wireless device are also disclosed. In someembodiments, a wireless device for a wireless system comprises aninterface operable to provide wireless communication between thewireless device and one or more network nodes, a processor, and storagecomprising instructions executable by the processor whereby the wirelessdevice is operable to operate as follows. The wireless device isoperable to receive, from a first network node via the interface, afirst message that instructs the wireless device to suspend a connectionbetween the wireless device and the wireless system. Upon receiving thefirst message, the wireless device stores a wireless device context ofthe wireless device and enters a suspended mode of operation. Thewireless device is further operable to, upon an occurrence of atriggering event, transmit, to a second network node via the interface,a second message that requests that the connection between the wirelessdevice and the wireless system be resumed. The second message comprisesa resume identifier, and the resume identifier comprises a part thatidentifies the first network node to which the wireless device wasconnected upon suspending the connection, and a part that identifies thewireless device. The wireless device is further operable to receive,from the second network node via the interface, a third message thatindicates that the connection between the wireless device and thewireless system is being resumed using the stored wireless devicecontext of the wireless device.

In some embodiments, a wireless device for a wireless system is adaptedto receive, from a first network node, a first message that instructsthe wireless device to suspend a connection between the wireless deviceand the wireless system where, upon receiving the first message, thewireless device stores a wireless device context of the wireless deviceand enters a suspended mode of operation. The wireless device is furtheradapted to, upon an occurrence of a triggering event, transmit, to asecond network node, a second message that requests that the connectionbetween the wireless device and the wireless system be resumed. Thesecond message comprises a resume identifier, and the resume identifiercomprises a part that identifies the first network node to which thewireless device was connected upon suspending the connection and a partthat identifies the wireless device. The wireless device is furtheradapted to receive, from the second network node, a third message thatindicates that the connection between the wireless device and thewireless system is being resumed using the stored wireless devicecontext of the wireless device. In some embodiments, the wireless deviceis further adapted to operate according to any one of the embodiments ofthe method of operation of the wireless device described herein.

In some embodiments, a wireless device for a wireless system comprises afirst receiving module, a transmitting module, and a second receivingmodule. The first receiving module is operable to receive, from a firstnetwork node, a first message that instructs the wireless device tosuspend a connection between the wireless device and the wireless systemwhere, upon receiving the first message, the wireless device stores awireless device context of the wireless device and enters a suspendedmode of operation. The transmitting module is operable to, upon anoccurrence of a triggering event, transmit, to a second network node, asecond message that requests that the connection between the wirelessdevice and the wireless system be resumed. The second message comprisesa resume identifier, and the resume identifier comprises a part thatidentifies the first network node to which the wireless device wasconnected upon suspending the connection and a part that identifies thewireless device. The second receiving module is operable to receive,from the second network node, a third message that indicates that theconnection between the wireless device and the wireless system is beingresumed using the stored wireless device context of the wireless device.

Embodiments of a method of operation of a network node in a wirelesssystem are also disclosed. In some embodiments, a method of operation ofa network node in a wireless system comprises receiving, from a wirelessdevice, a first message that requests that a connection between thewireless device and the wireless system be resumed. The first messagecomprises a resume identifier, and the resume identifier comprises apart that identifies a network node to which the wireless device wasconnected upon suspending the connection and a part that identifies thewireless device. The method further comprises obtaining, from thenetwork node identified by the resume identifier, a wireless devicecontext of the wireless device previously stored upon suspending theconnection between the wireless device and the wireless system. Themethod further comprises transmitting, to the wireless device, a secondmessage that indicates that the connection between the wireless deviceand the wireless system is being resumed using the stored wirelessdevice context of the wireless device.

In some embodiments, the network node is a first network node and thenetwork node identified by the resume identifier is a second networknode where the first network node and the second network node aredifferent network nodes. Further, in some embodiments, obtaining thewireless device context of the wireless device comprises sending arequest for the wireless device context of the wireless device to thesecond network node and receiving the wireless device context of thewireless device from the second network node. Further, in someembodiments, the request for the wireless device context of the wirelessdevice comprises the resume identifier.

In some embodiments, the second message comprises an authorization tokenthat allows the network node to securely identify the wireless device,and the method further comprises verifying the authorization token.

In some embodiments, the network node and the network node identified bythe resume identifier are the same network node, and obtaining thewireless device context of the wireless device comprises obtaining thewireless device context of the wireless device from storage.

In some embodiments, the wireless system is a LTE network, the part ofthe resume identifier that identifies the network node to which thewireless device was connected upon suspending the connection is an ECI,and the part of the resume identifier that identifies the wirelessdevice is a C-RNTI.

In some embodiments, an ordering of the parts within the resumeidentifier is such that the part of the resume identifier thatidentifies the network node to which the wireless device was connectedupon suspending the connection occurs first in the ordering and the partof the resume identifier that identifies the wireless device occursafter the part of the resume identifier that identifies the network nodeto which the wireless device was connected upon suspending theconnection in the ordering.

In some embodiments, an ordering of the parts within the resumeidentifier is such that the part of the resume identifier thatidentifies the wireless device occurs first in the ordering and the partof the resume identifier that identifies the network node to which thewireless device was connected upon suspending the connection occursafter the part of the resume identifier that identifies the wirelessdevice in the ordering.

In some embodiments, the resume identifier further comprises a part thatcontains a group identifier assigned to the wireless device. Further, insome embodiments, an ordering of the parts within the resume identifieris such that the part of the resume identifier that identifies thewireless device occurs first in the ordering, the part that contains thegroup identifier assigned to the wireless device occurs after the partof the resume identifier that identifies the wireless device in theordering, and the part of the resume identifier that identifies thenetwork node to which the wireless device was connected upon suspendingthe connection occurs after the part that contains the group identifierassigned to the wireless device in the ordering. In some embodiments,bit orders within the parts of the resume identifier are reversed.

In some embodiments, the second message that indicates that theconnection between the wireless device and the wireless system is beingresumed comprises a copy of the first message that requests that theconnection between the wireless device and the wireless system beresumed.

In some embodiments, a MAC control element associated with the secondmessage comprises a copy of the first message that requests that theconnection between the wireless device and the wireless system beresumed.

In some embodiments, a MAC control element associated with the secondmessage comprises a copy of a portion of the first message that requeststhat the connection between the wireless device and the wireless systembe resumed. Further, in some embodiments, the portion of the firstmessage comprises the part of the resume identifier that identifies thewireless device. In some embodiments, the first message furthercomprises an authorization token that allows the network node tosecurely identify the wireless device, and the portion of the firstmessage comprises the authorization token. In some embodiments, theresume identifier further comprises a part that contains a groupidentifier assigned to the wireless device, and the portion of the firstmessage comprises the part of the resume identifier that contains thegroup identifier. In some embodiments, the first message is transmittedin an uplink common control channel service data unit, and the portionof the first message is provided by truncating the uplink common controlchannel service data unit. In some embodiments, the first message istransmitted in an uplink common control channel service data unit, andthe portion of the first message is provided by truncating the uplinkcommon control channel service data unit to a size of an existingcontent resolution identity MAC control element in LTE. In someembodiments, the first message is transmitted in an uplink commoncontrol channel service data unit, and the portion of the first messageis provided by truncating the uplink common control channel service dataunit to 48 bits.

In some embodiments, the wireless device context comprises a bearerconfiguration of the wireless device and security related parameters.

In some embodiments, the network node is a first network node and thenetwork node identified by the resume identifier is a second networknode where the first network node and the second network node aredifferent network nodes.

In some embodiments, the network node and the network node identified bythe resume identifier are the same network node.

Embodiments of a network node for a wireless system are also disclosed.In some embodiments, a network node comprises an interface, a processor,and storage comprising instructions executable by the processor wherebythe network node is operable to operate as follows. The network node isoperable to receive, from a wireless device via the interface, a firstmessage that requests that a connection between the wireless device andthe wireless system be resumed. The first message comprises a resumeidentifier, and the resume identifier comprises a part that identifies anetwork node to which the wireless device was connected upon suspendingthe connection and a part that identifies the wireless device. Thenetwork node is further operable to obtain, from the network nodeidentified by the resume identifier, a wireless device context of thewireless device previously stored upon suspending the connection betweenthe wireless device and the wireless system. The network node is furtheroperable to transmit, to the wireless device via the interface, a secondmessage that indicates that the connection between the wireless deviceand the wireless system is being resumed using the stored wirelessdevice context of the wireless device.

In some embodiments, a network node for a wireless system is adapted toreceive, from a wireless device, a first message that requests that aconnection between the wireless device and the wireless system beresumed. The first message comprises a resume identifier, and the resumeidentifier comprises a part that identifies a network node to which thewireless device was connected upon suspending the connection and a partthat identifies the wireless device. The network node is further adaptedto obtain, from the network node identified by the resume identifier, awireless device context of the wireless device previously stored uponsuspending the connection between the wireless device and the wirelesssystem. The network node is further adapted to transmit, to the wirelessdevice, a second message that indicates that the connection between thewireless device and the wireless system is being resumed using thestored wireless device context of the wireless device. In someembodiments, the network node is further adapted to operate according tothe method of operation of a network node according to any one of theembodiments describe herein.

In some embodiments, a network node for a wireless system comprises areceiving module, an obtaining module, and a transmitting module. Thereceiving module is operable to receive, from a wireless device, a firstmessage that requests that a connection between the wireless device andthe wireless system be resumed. The first message comprises a resumeidentifier, and the resume identifier comprises a part that identifies anetwork node to which the wireless device was connected upon suspendingthe connection and a part that identifies the wireless device. Theobtaining module is operable to obtain, from the network node identifiedby the resume identifier, a wireless device context of the wirelessdevice previously stored upon suspending the connection between thewireless device and the wireless system. The transmitting module isoperable to transmit, to the wireless device, a second message thatindicates that the connection between the wireless device and thewireless system is being resumed using the stored wireless devicecontext of the wireless device.

In some embodiments, a method of operation of a wireless device in awireless system comprises receiving, from a first network node, a firstmessage that instructs the wireless device to suspend a connectionbetween the wireless device and the wireless system where, uponreceiving the first message, the wireless device stores a wirelessdevice context of the wireless device and enters a suspended mode ofoperation. The method further comprises, upon an occurrence of atriggering event, transmitting, to a second network node, a secondmessage that requests that the connection between the wireless deviceand the wireless system be resumed, the second message comprising aresume identifier. The method further comprises receiving, from thesecond network node, a third message that indicates that the connectionbetween the wireless device and the wireless system is being resumedusing the stored wireless device context of the wireless device. A MACcontrol element associated with the third message comprises a copy of aportion of the second message that requests that the connection betweenthe wireless device and the wireless system be resumed. Further, thesecond message is transmitted in an uplink common control channelservice data unit, and the portion of the second message is a truncatedversion of the uplink common control channel service data unit.

Those skilled in the art will appreciate the scope of the presentdisclosure and realize additional aspects thereof after reading thefollowing detailed description of the embodiments in association withthe accompanying drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawing figures incorporated in and forming a part ofthis specification illustrate several aspects of the disclosure, andtogether with the description serve to explain the principles of thedisclosure.

FIG. 1 illustrates a process by which a Radio Resource Control (RRC)connection of a User Equipment device (UE) is suspended;

FIG. 2 illustrates a process by which a suspended RRC connection of a UEis resumed;

FIG. 3 illustrates one example of a wireless network in whichembodiments of the present disclosure may be implemented;

FIG. 4 is a signaling diagram that illustrates the operation of thewireless network of FIG. 3 according to some embodiments of the presentdisclosure;

FIG. 5 illustrates an example of a wireless device (e.g., a UE)according to some other embodiments of the present disclosure; and

FIGS. 6 and 7 illustrate examples of a network node (e.g., a basestation) according to some other embodiments of the present disclosure.

DETAILED DESCRIPTION

The embodiments set forth below represent information to enable thoseskilled in the art to practice the embodiments and illustrate the bestmode of practicing the embodiments. Upon reading the followingdescription in light of the accompanying drawing figures, those skilledin the art will understand the concepts of the disclosure and willrecognize applications of these concepts not particularly addressedherein. It should be understood that these concepts and applicationsfall within the scope of the disclosure and the accompanying claims.

As discussed above, Radio Resource Control (RRC) Resume is a featurethat reduces signaling overhead when a User Equipment (UE) transitionsfrom RRC IDLE to RRC CONNECTED. RRC Resume is particularly beneficialfor UEs, such as Machine Type Communication (MTC) devices, that performinfrequent transmissions of small amounts of data, but is not limitedthereto. RRC Resume is based on re-using a UE context from the previousRRC connection for the UE when setting up a subsequent RRC connectionfor that UE. By storing the UE context in the enhanced or evolved Node B(eNB) to which the UE was connected when the UE's RRC connection wassuspended (i.e., the suspending eNB), the UE context can be re-used whenresuming the UE's RRC connection, thereby reducing signaling overhead.

One problem with RRC Resume when supporting inter-eNB connectionresumption is that the resuming eNB (i.e., the eNB to which the UE isconnecting when resuming the RRC connection) must fetch the UE contextof the UE from the suspending eNB. A Resume identifier (ID) isassociated with the UE for RRC Resume. The Resume ID enables the UE tobe identified. The present disclosure relates to systems and methodsthat utilize a format for the Resume ID that identifies both the UE andthe suspending eNB.

More specifically, the format of Resume ID for RRC Resume is stillunspecified. As proposed in this disclosure, the Resume ID should firstof all act as an identifier for the UE context of suspended UEs. Thisputs requirements on its length since it has to be large enough toaddress all the suspended UEs within a cell/eNB. Secondly, it isproposed that in order to support inter-eNB RRC resume, the Resume IDshould allow the resuming eNB to identify the eNB which suspended theconnection so that the UE context can be fetched. Furthermore, thisdisclosure proposes that the Resume ID should preferably be based onexisting Long Term Evolution (LTE) identifiers to reduce signalingoverhead.

Embodiments of a system and method for identifying and retrieving the UEcontext of a suspended UE when an RRC connection is resumed aredisclosed. The identifier for the UE context, i.e., the so called ResumeID, is made up of two parts, where the first part identifies the eNB andcell and the second part identifies the suspended UE within a cell. Aswill be appreciated by one of skill in the art, the first part of theResume ID may identify the eNB, the cell, or both the eNB and the cell,depending on the particular implementation. This enables the use of RRCResume, which is an important signaling reduction technique in LTE.

According to particular embodiments, the first part of the Resume ID isthe 28 bit Evolved Universal Terrestrial Radio Access Network (E-UTRAN)Cell ID (ECI) broadcasted in System Information Block (SIB) SIB1, andthe second part of the Resume ID is the 16 bit Cell Radio NetworkTemporary Identifier (C-RNTI) assigned to the UE as part of the randomaccess procedure. Note that C-RNTI is only one example of a networkassigned UE identifier. Further note that, as will be understood by oneof skill in the art, the ECI includes both the eNB ID and the UE ID and,as such, the first part of the Resume ID may include only the portion ofthe ECI, or cell ID, that identifies the eNB, in some embodiments.According to alternative embodiments, and to increase likeliness for nomore than one UE using the same identifier when a truncated version ofthe Resume ID is used during contention resolution, the two parts can beswapped such that UE identity within a cell is the first part of theResume ID and the eNB and cell identifier is the second part of theResume ID. Together these two identifiers allow a suspended UE to beuniquely identified within a radio access network. Furthermore, sinceboth identifiers are already known to the UE, there is no need to signalthe Resume ID to the UE when the RRC connection is suspended.

The 16-bit C-RNTI allows up to 65,536 UEs to be suspended in a cellbefore the address space is depleted. Since this this may not be enoughfor wide area cells containing many UEs, a group identifier canoptionally be appended to the C-RNTI to increase the address space. Thegroup identifier can be signaled to the UE either in the initialestablishment of the RRC connection and when the RRC connection isresumed or when the RRC connection is suspended.

The proposed solutions have the following advantages:

-   -   Enables the use of RRC Resume across multiple eNBs/cells.    -   Since the Resume ID is based on existing identifiers which are        already known to the UE, there is no need to signal the Resume        ID to the UE when a connection is suspended. This leads to a        simpler solution and reduces signaling overhead. Furthermore,        using existing identifiers also has the benefit that it requires        less specification effort.    -   By using the optional group identifier, a larger number of        suspended UEs can be supported. This is important for wide area        cells and/or dense UE deployments.    -   In some embodiments, ambiguity (in contention resolution due to        a new identifier) is avoided for legacy UEs which do not        implement or understand the new functionality; i.e., legacy UEs        can be kept unaffected.

As described above, this disclosure proposes improved methods of RRCResume for use within a wireless network, especially operating acrossmultiple eNBs/cells in said network. FIG. 3 illustrates an exemplarywireless network 10 in which these embodiments may be carried out,comprising a network 12 which may also be referred to a core network,network nodes 14-1 and 14-2 which may generally be referred to herein asnetwork nodes 14, and a wireless device (WD) 16. In the illustratedexample, the network nodes 14 are, more specifically, radio access nodesand, in this example, base stations. As such, the network nodes 14 arealso referred to herein as base stations 14. In LTE, base stations arereferred to as eNBs. So, the network nodes 14 are also referred toherein as eNBs 14. FIG. 3 comprises more detailed views of the networknode 14-1 and the WD 16, in accordance with a particular embodiment. Thenetwork node 14-1 comprises a processor 18, storage 20, an interface 22,and an antenna 24. Similarly, the WD 16 comprises a processor 26,storage 28, an interface 30, and an antenna 32. These components maywork together in order to provide network node and/or wireless devicefunctionality, such as providing wireless connections in the wirelessnetwork 10. In different embodiments, the wireless network 10 maycomprise any number of wired or wireless networks, network nodes, basestations, controllers, wireless devices, relay stations, and/or anyother components that may facilitate or participate in the communicationof data and/or signals whether via wired or wireless connections.

The network 12 may comprise one or more Internet Protocol (IP) networks,Public Switched Telephone Networks (PSTNs), packet data networks,optical networks, Wide Area Networks (WANs), Local Area Networks (LANs),Wireless Local Area Networks (WLANs), wired networks, wireless networks,metropolitan area networks, and other networks to enable communicationbetween devices.

The network node 14-1 comprises the processor 18, the storage 20, theinterface 22, and the antenna 24. For the purposes of illustration,these components are depicted as single boxes located within a singlelarger box. In practice however, a network node may comprise multipledifferent physical components that make up a single illustratedcomponent (e.g., the interface 22 may comprise terminals for couplingwires for a wired connection and a radio transceiver for a wirelessconnection). Similarly, the network node 14-1 may be composed ofmultiple physically separate components (e.g., a Node B component and aRadio Network Controller (RNC) component, a Base Transceiver Station(BTS) component and a Base Station Controller (BSC) component, etc.),which may each have their own respective processor, storage, andinterface components. In certain scenarios in which the network node14-1 comprises multiple separate components (e.g., BTS and BSCcomponents), one or more of the separate components may be shared amongseveral network nodes. For example, a single RNC may control multipleNode Bs. In such a scenario, each unique Node B and BSC pair may be aseparate network node. In some embodiments, the network node 14-1 may beconfigured to support multiple Radio Access Technologies (RATs). In suchembodiments, some components may be duplicated (e.g., separate storage20 for the different RATs) and some components may be reused (e.g., thesame antenna 24 may be shared by the RATs).

The processor 18 may be a combination of one or more of amicroprocessor, controller, microcontroller, Central Processing Unit(CPU), digital signal processor, Application Specific Integrated Circuit(ASIC), Field Programmable Gate Array (FPGA), or any other suitablecomputing device, resource, or combination of hardware, software, and/orencoded logic operable to provide, either alone or in conjunction with,other network node 14-1 components, such as storage 20, and network node14-1 functionality. For example, the processor 18 may executeinstructions stored in the storage 20. Such functionality may includeproviding various wireless features discussed herein to a wirelessdevice, such as the WD 16, including any of the features or benefitsdisclosed herein.

The storage 20 may comprise any form of volatile or non-volatilecomputer readable memory including, without limitation, persistentstorage, solid state memory, remotely mounted memory, magnetic media,optical media, Random Access Memory (RAM), Read-Only Memory (ROM),removable media, or any other suitable local or remote memory component.The storage 20 may store any suitable instructions, data, orinformation, including software and encoded logic, utilized by thenetwork node 14-1. The storage 20 may be used to store any calculationsmade by the processor 18 and/or any data received via the interface 22.

The network node 14-1 also comprises the interface 22 which may be usedin the wired or wireless communication of signaling and/or data betweenthe network node 14-1, the network 12, and/or the WD 16. For example,the interface 22 may perform any formatting, coding, or translating thatmay be needed to allow the network node 14-1 to send and receive datafrom the network 12 over a wired connection. The interface 22 may alsoinclude a radio transmitter and/or receiver that may be coupled to or apart of the antenna 24. The radio may receive digital data that is to besent out to other network nodes or WDs via a wireless connection. Theradio may convert the digital data into a radio signal having theappropriate channel and bandwidth parameters. The radio signal may thenbe transmitted via the antenna 24 to the appropriate recipient (e.g.,the WD 16).

The antenna 24 may be any type of antenna capable of transmitting andreceiving data and/or signals wirelessly. In some embodiments, theantenna 24 may comprise one or more omni-directional, sector, or panelantennas operable to transmit/receive radio signals. An omni-directionalantenna may be used to transmit/receive radio signals in any direction,a sector antenna may be used to transmit/receive radio signals fromdevices within a particular area, and a panel antenna may be a line ofsight antenna used to transmit/receive radio signals in a relativelystraight line.

The WD 16 may be any type of wireless endpoint, wireless machine, mobilestation, mobile phone, wireless local loop phone, smartphone, UE,desktop computer, Personal Digital Assistant (PDA), cell phone, tablet,laptop, or Voice over IP (VoIP) phone or handset, which is able towirelessly send and receive data and/or signals to and from a networknode, such as the network node 14-1, and/or other WDs. The WD 16comprises the processor 26, the storage 28, the interface 30, and theantenna 32. Like the network node 14-1, the components of the WD 16 aredepicted as single boxes located within a single larger box; however, inpractice a wireless device may comprises multiple different physicalcomponents that make up a single illustrated component (e.g., thestorage 28 may comprise multiple discrete microchips, each microchiprepresenting a portion of the total storage capacity).

The processor 26 may be a combination of one or more of amicroprocessor, controller, microcontroller, CPU, digital signalprocessor, ASIC, FPGA, or any other suitable computing device, resource,or combination of hardware, software, and/or encoded logic operable toprovide, either alone or in combination with other WD 16 components,such as the storage 28, WD 16 functionality. Such functionality mayinclude providing various wireless features discussed herein, includingany of the features or benefits disclosed herein.

The storage 28 may be any form of volatile or non-volatile memoryincluding, without limitation, persistent storage, solid state memory,remotely mounted memory, magnetic media, optical media, RAM, ROM,removable media, or any other suitable local or remote memory component.The storage 28 may store any suitable data, instructions, orinformation, including software and encoded logic, utilized by the WD16. The storage 28 may be used to store any calculations made by theprocessor 26 and/or any data received via the interface 30.

The interface 30 may be used in the wireless communication of signalingand/or data between the WD 16 and the network node 14-1. For example,the interface 30 may perform any formatting, coding, or translating thatmay be needed to allow the WD 16 to send and receive data from thenetwork node 14-1 over a wireless connection. The interface 30 may alsoinclude a radio transmitter and/or receiver that may be coupled to or apart of the antenna 32. The radio may receive digital data that is to besent out to the network node 14-1 via a wireless connection. The radiomay convert the digital data into a radio signal having the appropriatechannel and bandwidth parameters. The radio signal may then betransmitted via the antenna 32, to the network node 14-1.

The antenna 32 may be any type of antenna capable of transmitting andreceiving data and/or signals wirelessly. In some embodiments, theantenna 32 may comprise one or more omni-directional, sector, or panelantennas operable to transmit/receive radio signals. For simplicity, theantenna 32 may be considered a part of the interface 30 to the extentthat a wireless signal is being used.

Any steps described herein are merely illustrative of certainembodiments. It is not required that all embodiments incorporate all thesteps disclosed nor that the steps be performed in the exact orderdepicted or described herein. Furthermore, some embodiments may includesteps not illustrated or described herein, including steps inherent toone or more of the steps disclosed herein.

Any appropriate steps, methods, or functions may be performed through acomputer program product that may, for example, be executed by thecomponents and equipment illustrated in FIG. 3. For example, the storage20 may comprise computer readable means on which a computer program canbe stored. The computer program may include instructions which cause theprocessor 18 (and any operatively coupled entities and devices, such asthe interface 22 and the storage 20) to execute methods according toembodiments described herein. The computer program and/or computerprogram product may thus provide means for performing any steps hereindisclosed.

Any appropriate steps, methods, or functions may be performed throughone or more functional modules. Each functional module may comprisesoftware, computer programs, sub-routines, libraries, source code, orany other form of executable instructions that are executed by, forexample, a processor. In some embodiments, each functional module may beimplemented in hardware and/or in software. For example, one or more orall functional modules may be implemented by the processors 26 and/or18, possibly in cooperation with the storage 28 and/or 20. Theprocessors 26 and/or 18 and the storage 28 and/or 20 may thus bearranged to allow the processors 26 and/or 18 to fetch instructions fromthe storage 28 and/or 20 and execute the fetched instructions to allowthe respective functional module to perform any steps or functionsdisclosed herein.

A description is provided below of the basic steps performed in thewireless device 16, the network node 14 (referred to herein as thesuspending network node) suspending a connection of the wireless device16 to the radio access network, and the network node 14 (referred toherein as the resuming network node) resuming the connection of thewireless device 16 to the radio access network. In this followingexample, the wireless network 10 is a Third Generation PartnershipProject (3GPP) LTE or future variation thereof and, as such, 3GPPterminology is used. Therefore, the wireless device 16 is referred to asUE 16, the suspending network node 14 is referred to as the suspendingeNB 14, and the resuming network node 14 is referred to as the resumingeNB 14. Further, in the following example, the eNB 14-1 is the resumingeNB, and the eNB 14-2 is the suspending eNB. The description is madewith reference to the signaling diagram in FIG. 4.

The UE 16 has an established RRC connection with a source eNB 14-2. Dueto some trigger (e.g., expiry of an UE inactivity timer), the source eNB14-2 decides to suspend the RRC connection by sending a RRC ConnectionSuspend message to the UE 16 (step 100). The eNB 14-2 is thereforereferred to as the suspending eNB 14-2. The UE 16 stores its UE contextand transitions to IDLE/SUSPENDED state upon receiving the RRCConnection Suspend message. Various triggers may be envisioned thatwould cause the eNB 14-2 to suspend the RRC connection. The RRCConnection Suspend message may contain security related parameters(e.g., Next Hop Chaining Counter (NCC) and security algorithmconfiguration) which are required when Access Stratum (AS) security islater re-established. This information is stored by the UE 16 inaddition to its UE context.

If the cell served by the suspending eNB 14-2 is large and contains manysuspended UEs, the suspending eNB 14-2 can assign a GROUP_ID to increasethe number of addressable UE contexts. The GROUP_ID is either includedin the RRC Connection Suspend message or the GROUP_ID is sent to the UE16 when the RRC connection was initially established, e.g. in the secondstep of the RRC Connection Establishment procedure. In case the GROUP_IDis sent to the UE 16 during the connection establishment procedure, theGROUP_ID may also be included, or sent, in the RRC Connection Resumemessage to allow for change of the GROUP_ID to ensure that thecombination of the GROUP_ID and the UE identity within the new cell(i.e., the cell in which the RRC connection is subsequently resumed) isunique within the new cell; i.e., not used for any other UE in the newcell.

The UE 16 remains in IDLE/SUSPENDED state until new uplink (UL) dataarrives (i.e., new data arrives in the uplink buffer of the UE 16) orthe UE 16 is paged (step 102). At some later point in time, new dataarrives in the uplink buffer at the UE 16 or the UE 16 is being paged bythe network 12. This, or any other activity that would require aconnection with the UE 16, triggers the UE 16 to resume the RRCconnection. Optionally, in some scenarios, the UE 16 performs a randomaccess procedure in which the UE 16 transmits a random access preamble(step 104) and, in response, receives a random access response from theeNB 14-1 (step 106). The UE 16 resumes its RRC connection by sending anRRC Connection Resume Request message to the eNB 14-1, which is referredto as the target or resuming eNB (step 108). The UE 16 includes itsResume ID and an authorization token in the RRC Connection ResumeRequest message.

As discussed above, the Resume ID is made up of two or three parts,depending on the embodiment. One part identifies the eNB and cell andanother part identifies the suspended UE within a cell. In someembodiments, the Resume ID includes another part that is a groupidentifier. In some particular embodiments, the Resume ID is a compositeidentifier made up of the following sub-parts:

-   -   ECI. The ECI is 28 bits long and is broadcasted in SIB1 of the        suspending cell. It can be used to uniquely identify an eNB and        cell within a Public Land Mobile Network (PLMN).    -   C-RNTI. The C-RNTI is 16 bits long and is assigned by the        suspending cell during the random access procedure.    -   GROUP_ID. GROUP_ID is a new identifier which is used to expand        the address space if the 16 bit C-RNTI is not sufficient. It is        assigned to the UE 16 by the suspending eNB 14-2 as explained in        step 100.

The resuming eNB 14-1 locates the suspending eNB 14-2 based on the ECIand sends a request to retrieve the UE context associated with the UE 16(step 110). The UE context request includes the Resume ID of the UE 16.In some alternative embodiments, rather than including the full ResumeID, the UE context request may include the C-RNTI and, if included, theGROUP_ID of the UE 16.

The suspending eNB 14-2 retrieves the UE context associated with theC-RNTI and GROUP_ID (if present) and sends the UE context to theresuming eNB 14-1 (step 112). The UE context response also includes theAS security key, the security algorithm configuration, and theauthorization token.

In case no UE context is found, the suspending eNB 14-2 responds with anerror message indicating that the Resume ID is missing.

If the UE context was found, the resuming eNB 14-1 verifies theauthorization token received from the UE 16 in the RRC Connection ResumeRequest message by matching it to the authorization token received fromthe suspending eNB 14-2 (step 114). Next, the resuming eNB 14-1activates AS security using the AS security key and the securityalgorithm configuration received from the suspending eNB 14-2 (step114).

The resuming eNB 14-1 sends a RRC Connection Resume message to the UE 16to indicate that the connection is being resumed (step 116).

Note that contention resolution may also be performed as part of thisstep. In case multiple UEs perform random access at the same time andselect the same preamble, they will all receive the same random accessresponse and will therefore use the same resources for the uplinktransmission. In this case, the eNB will receive multiple RRC ConnectionResume Request messages but it may only be able to decode and respond toone of them. In order for a UE to be able to determine which UE the eNBactually responded to, the eNB includes a copy of the RRC ConnectionResume Request in its response. Only a UE which observes a match betweenthe received and transmitted message, i.e., the RRC Connection ResumeRequest, will declare the random access procedure successful. Thus, inorder determine whether there is a match, the UE 16 compares the copy ofthe RRC Connection Resume Request included in the RRC Connection Resumemessage to a local copy of the RRC Connection Resume Request forpurposes of content resolution. If there is a match between the receivedcopy and the local copy, then the UE 16 will declare the random accessprocedure successful. Since the RRC Connection Resume Request containsthe Resume ID which is unique among UEs, only one UE will be successful.The other UEs will restart from the beginning.

Contention resolution could be performed by the Medium Access Control(MAC) layer in the same way as is done today for RRC connectionestablishment/re-establishment, i.e. the copy of the RRC ConnectionResume Request is transmitted in the contention resolution identity MACcontrol element. One problem though is that the size of this controlelement is fixed to 48 bits which is less than the size of the RRCConnection Resume Request. There are two primary options for handlingthis problem:

-   -   Introduce a new contention resolution identity MAC control        element with a larger size; and    -   Use the existing contention resolution identity MAC control        element but only parts of the content from RRC Connection Resume        Request message is copied (e.g., the C-RNTI, GROUP-ID (if        needed), and authorization token). Thus, at the UE 16, the UE 16        will declare the random access procedure successful if there is        a match between the portion of the RRC Connection Resume Request        message included in the RRC Connection Resume message and a        local copy of that portion of the RRC Connection Resume Request.

In the latter case, the contention resolution identity may no longer beunique and there is a small risk that contention resolution succeeds formore than one UE. However, since AS security is activated and only theUE with the correct key will be able to decipher and verify theintegrity of subsequent messages, this situation can be detected andresolved.

Copying parts of the content from the RRC Connection Resume Requestmessage can be done, e.g.:

-   -   by including only specific information elements and/or parts of        information elements; or    -   by copying the first part of the RRC Connection Resume message,        comprising identification of the RRC message type, and specific        information elements and/or parts of information elements; or    -   by truncation of the RRC Connection Resume Request message        (Service Data Unit (SDU) from the Common Control Channel (CCCH))        to the size of the existing contention resolution identity MAC        control element (i.e., 48 bits in legacy LTE).

By truncating the SDU from CCCH, the message type included in the RRCmessage is kept, and it can be ensured that the contention resolutionidentities for legacy RRC Connection Request, RRC ConnectionReestablishment Request, and RRC Connection Resume Request can bedistinguished by means of the message type of the UL-CCCH included inthe RRC message. Hence, in the case truncated SDU from CCCH is used ascontention resolution identity, ambiguity is avoided for legacy UEswhich do not implement or understand the new functionality; i.e., legacyUEs can be kept unaffected. In case the truncated SDU from CCCH would nolonger present a unique contention resolution identity among UEsattempting to resume RRC Connections, conflict can be detected andresolved by verification of AS integrity as described above. The risk ofconflicts can be reduced by arranging the information included in theRRC Connection Resume Request in an order such that entropy in thecontention resolution identity MAC control element becomes high; i.e.,unlikely that more than one UE uses the same contention resolutionidentity at the same time in the same cell. In an exemplary arrangementof the information in the Resume ID, the first part can be C-RNTIfollowed by GROUP_ID (if GROUP_ID is needed/used) and ECI. To furtherincrease entropy in the contention resolution identity MAC controlelement, e.g., in case it is based on a truncated RRC Connection Resumemessage, the bit orders in the C-RNTI, GROUP_ID, and ECI parts can bereversed so that, e.g., the cell identity part of ECI comes before theeNB part of ECI. Reversing the bit order of the C-RNTI and GROUP_IDparts is assuming that they are allocated incrementally and thedistribution is biased towards smaller values. Alternatively toreversing bit orders of C-RNTI and GROUP_ID, the allocation algorithmcan be adapted to achieve the same result.

The UE may acknowledge the reception by sending a RRC Connection ResumeComplete message (step 118). Note that step 118 is optional. The UE 16is then in the RRC CONNECTED state and may then transmit uplink data(step 120) and receive downlink data (step 122) using the resumed RRCconnection.

In the description above, it is assumed that the suspending eNB 14-2 isdifferent from the resuming eNB 14-1, i.e., inter-eNB RRC resume isassumed. In case the suspending and resuming eNBs 14 are identical, orthe same eNB 14, i.e., assuming an intra-eNB RRC resume, the procedureis the same except that steps 110 and 112 are performed internally inthe eNB 14.

Certain aspects of the present disclosure have mainly been describedabove with reference to a few embodiments. However, as is readilyappreciated by a person skilled in the art, embodiments other than theones disclosed above are equally possible and within the scope of thepresent disclosure and the concepts disclosed herein. Similarly, while anumber of different combinations have been discussed, all possiblecombinations have not been disclosed. One skilled in the art wouldappreciate that other combinations exist and are within the scope of thepresent disclosure. Moreover, as is understood by the skilled person,the herein disclosed embodiments are as such applicable also to otherstandards and communication systems and any feature from a particularfigure disclosed in connection with other features may be applicable toany other figure and or combined with different features.

As discussed above, any appropriate steps, methods, or functions may beperformed through one or more functional modules. Each functional modulemay comprise software, computer programs, sub-routines, libraries,source code, or any other form of executable instructions that areexecuted by, for example, a processor. In some embodiments, eachfunctional module may be implemented in hardware and/or in software. Forexample, one or more or all functional modules may be implemented by theprocessors 26 and/or 18, possibly in cooperation with the storage 28and/or 20. The processors 26 and/or 18 and the storage 28 and/or 20 maythus be arranged to allow the processors 26 and/or 18 to fetchinstructions from the storage 28 and/or 20 and execute the fetchedinstructions to allow the respective functional module to perform anysteps or functions disclosed herein.

In this regard, FIGS. 5 through 7 illustrate example embodiments of thewireless device 16 and the network node 14. As illustrated in FIG. 5, inthis example, the wireless device 16 includes a first receiving module34-1, a transmitting module 34-2, and a second receiving module 34-3.The first receiving module 34-1 is operable to receive, from a firstnetwork node 14, a first message that instructs the wireless device 16to suspend a connection between the wireless device 16 and the wirelessnetwork 10. Upon receiving the first message, the wireless device 16stores a wireless device context (i.e., a UE context) of the wirelessdevice 16 and enters a suspended mode of operation. The transmittingmodule 34-2 is operable to, upon an occurrence of a triggering event,transmit, to a second network node 14, a second message that requeststhat the connection between the wireless device 16 and the wirelessnetwork 16 be resumed. The second message includes a resume identifier,where the resume identifier includes a part that identifies the firstnetwork node 14 to which the wireless device 16 was connected uponsuspending the connection and a part that identifies the wireless device16. The second receiving module 34-3 is operable to receive, from thesecond network node 14, a third message that indicates that theconnection between the wireless device 16 and the wireless network 10 isbeing resumed using the stored wireless device context of the wirelessdevice 16.

As illustrated in FIG. 6, in this example, the network node 14 includesa receiving module 36-1, an obtaining module 36-2, and a transmittingmodule 36-3. The receiving module 36-1 is operable to receive, from awireless device 16, a first message that requests that a connectionbetween the wireless device 16 and the wireless network 10 be resumed.The first message includes a resume identifier, where the resumeidentifier includes a part that identifies a network node 14 and cell towhich the wireless device 16 was connected upon suspending theconnection and a part that identifies the wireless device 16 within thecell. The obtaining module 36-2 is operable to obtain, from the networknode 14 identified by the resume identifier, a wireless device contextof the wireless device 16 previously stored upon suspending theconnection between the wireless device 16 and the wireless network 10.The transmitting module 36-3 is operable to transmit, to the wirelessdevice 16, a second message that indicates that the connection betweenthe wireless device 16 and the wireless network 10 is being resumedusing the stored wireless device context of the wireless device 16.

FIG. 7 is a schematic block diagram that illustrates a virtualizedembodiment of the base station 14 according to some embodiments of thepresent disclosure. Other types of network nodes may have similararchitectures (particularly with respect to including processor(s),memory, and a network interface).

As used herein, a “virtualized” base station 14 is a base station 14 inwhich at least a portion of the functionality of the base station 14 isimplemented as a virtual component (e.g., via a virtual machine(s)executing on a physical processing node(s) in a network(s)). Asillustrated, the base station 14 optionally includes a control system 38that includes the processor 18, the storage 20, and the networkinterface 22A, as described above. The base station 14 also includes atransceiver 22B, which may also be referred to as a radio interface,that includes one or more transmitters 40 and one or more receivers 42coupled to a number of antennas 24. The control system 38 (if present)is connected to the transceiver 22B via, for example, an optical cableor the like. The control system 38 (if present) is connected to one ormore processing nodes 44 coupled to or included as part of a network(s)46 via the network interface 22A. Alternatively, if the control system38 is not present, the transceiver 22B is connected to the one or moreprocessing nodes 44 via a network interface(s). Each processing node 44includes one or more processors 48 (e.g., CPUs, ASICs, FPGAs, and/or thelike), storage 50 (e.g., memory), and a network interface 52.

In this example, functions 54 of the base station 14 described hereinare implemented at the one or more processing nodes 44 or distributedacross the control system 38 (if present) and the one or more processingnodes 44 in any desired manner. In some particular embodiments, some orall of the functions 54 of the base station 14 described herein areimplemented as virtual components executed by one or more virtualmachines implemented in a virtual environment(s) hosted by theprocessing node(s) 44. As will be appreciated by one of ordinary skillin the art, additional signaling or communication between the processingnode(s) 44 and the control system 38 (if present) or alternatively thetransceiver 22B is used in order to carry out at least some of thedesired functions. Notably, in some embodiments, the control system 38may not be included, in which case the transceiver 22B communicatesdirectly with the processing node(s) 44 via an appropriate networkinterface(s).

The following acronyms are used throughout this disclosure.

-   -   3GPP Third Generation Partnership Project    -   AS Access Stratum    -   ASIC Application Specific Integrated Circuit    -   BSC Base Station Controller    -   BTS Base Transceiver Station    -   CCCH Common Control Channel    -   CPU Central Processing Unit    -   C-RNTI Cell Radio Network Temporary Identifier    -   ECI Evolved Universal Terrestrial Radio Access Network Cell        Identifier    -   eNB Enhanced or Evolved Node B    -   E-UTRAN Evolved Universal Terrestrial Radio Access Network    -   FPGA Field Programmable Gate Array    -   ID Identifier    -   IP Internet Protocol    -   LAN Local Area Network    -   LTE Long Term Evolution    -   MAC Medium Access Control    -   MTC Machine Type Communication    -   NCC Next Hop Chaining Counter    -   PDA Personal Digital Assistant    -   PLMN Public Land Mobile Network    -   PSTN Public Switched Telephone Network    -   RAM Random Access Memory    -   RAT Radio Access Technology    -   RNC Radio Network Controller    -   ROM Read-Only Memory    -   RRC Radio Resource Control    -   SDU Service Data Unit    -   SIB System Information Block    -   UE User Equipment    -   VoIP Voice over Internet Protocol    -   WAN Wide Area Network    -   WD Wireless Device    -   WLAN Wireless Local Area Network

Those skilled in the art will recognize improvements and modificationsto the embodiments of the present disclosure. All such improvements andmodifications are considered within the scope of the concepts disclosedherein and the claims that follow.

1. A method of operation of a wireless device in a wireless network,comprising: receiving, from a first network node, a first message thatinstructs the wireless device to suspend a connection between thewireless device and the wireless network where, upon receiving the firstmessage, the wireless device stores a wireless device context of thewireless device and enters a suspended mode of operation; upon anoccurrence of a triggering event, transmitting, to a second networknode, a second message that requests that the connection between thewireless device and the wireless network be resumed, the second messagecomprising a resume identifier and the resume identifier comprising: apart that identifies the first network node to which the wireless devicewas connected upon suspending the connection; and a part that identifiesthe wireless device; and receiving, from the second network node, athird message that indicates that the connection between the wirelessdevice and the wireless network is being resumed using the storedwireless device context of the wireless device.
 2. (canceled) 3.(canceled)
 4. (canceled)
 5. (canceled)
 6. (canceled)
 7. (canceled) 8.(canceled)
 9. (canceled)
 10. The method of claim 1 wherein a MediumAccess Control (MAC) control element associated with the third messagecomprises a copy of a portion of the second message that requests thatthe connection between the wireless device and the wireless network beresumed.
 11. The method of claim 10 wherein the portion of the secondmessage comprises the part of the resume identifier that identifies thewireless device.
 12. (canceled)
 13. (canceled)
 14. The method of claim10 wherein the second message is transmitted in an uplink common controlchannel service data unit, and the portion of the second message isprovided by truncating the uplink common control channel service dataunit.
 15. The method of claim 10 wherein the second message istransmitted in an uplink common control channel service data unit, andthe portion of the second message is provided by truncating the uplinkcommon control channel service data unit to a size of an existingcontent resolution identity MAC control element in LTE.
 16. The methodof claim 10 wherein the second message is transmitted in an uplinkcommon control channel service data unit, and the portion of the secondmessage is provided by truncating the uplink common control channelservice data unit to 48 bits.
 17. (canceled)
 18. (canceled) 19.(canceled)
 20. A wireless device for a wireless network, comprising: aninterface operable to provide wireless communication between thewireless device and one or more network nodes; a processor; and storagecomprising instructions executable by the processor whereby the wirelessdevice is operable to: receive, from a first network node via theinterface, a first message that instructs the wireless device to suspenda connection between the wireless device and the wireless network where,upon receiving the first message, the wireless device stores a wirelessdevice context of the wireless device and enters a suspended mode ofoperation; upon an occurrence of a triggering event, transmit, to asecond network node via the interface, a second message that requeststhat the connection between the wireless device and the wireless networkbe resumed, the second message comprising a resume identifier and theresume identifier comprising: a part that identifies the first networknode to which the wireless device was connected upon suspending theconnection; and a part that identifies the wireless device; and receive,from the second network node via the interface, a third message thatindicates that the connection between the wireless device and thewireless network is being resumed using the stored wireless devicecontext of the wireless device.
 21. (canceled)
 22. (canceled) 23.(canceled)
 24. A method of operation of a network node in a wirelessnetwork, comprising: receiving, from a wireless device, a first messagethat requests that a connection between the wireless device and thewireless network be resumed, the first message comprising a resumeidentifier and the resume identifier comprising: a part that identifiesa network node to which the wireless device was connected uponsuspending the connection; and a part that identifies the wirelessdevice; and obtaining, from the network node identified by the resumeidentifier, a wireless device context of the wireless device previouslystored upon suspending the connection between the wireless device andthe wireless network; and transmitting, to the wireless device, a secondmessage that indicates that the connection between the wireless deviceand the wireless network is being resumed using the stored wirelessdevice context of the wireless device.
 25. (canceled)
 26. (canceled) 27.(canceled)
 28. (canceled)
 29. (canceled)
 30. (canceled)
 31. (canceled)32. (canceled)
 33. (canceled)
 34. (canceled)
 35. (canceled) 36.(canceled)
 37. The method of claim 24 wherein a Medium Access Control(MAC) control element associated with the second message comprises acopy of a portion of the first message that requests that the connectionbetween the wireless device and the wireless network be resumed.
 38. Themethod of claim 37 wherein the portion of the first message comprisesthe part of the resume identifier that identifies the wireless device.39. (canceled)
 40. (canceled)
 41. The method of claim 37 wherein thefirst message is transmitted in an uplink common control channel servicedata unit, and the portion of the first message is provided bytruncating the uplink common control channel service data unit.
 42. Themethod of claim 37 wherein the first message is transmitted in an uplinkcommon control channel service data unit, and the portion of the firstmessage is provided by truncating the uplink common control channelservice data unit to a size of an existing content resolution identityMAC control element in LTE.
 43. The method of claim 37 wherein the firstmessage is transmitted in an uplink common control channel service dataunit, and the portion of the first message is provided by truncating theuplink common control channel service data unit to 48 bits. 44.(canceled)
 45. (canceled)
 46. (canceled)
 47. A network node for awireless network, comprising: an interface; a processor; and storagecomprising instructions executable by the processor whereby the networknode is operable to: receive, from a wireless device via the interface,a first message that requests that a connection between the wirelessdevice and the wireless network be resumed, the first message comprisinga resume identifier and the resume identifier comprising: a part thatidentifies a network node to which the wireless device was connectedupon suspending the connection; and a part that identifies the wirelessdevice; and obtain, from the network node identified by the resumeidentifier, a wireless device context of the wireless device previouslystored upon suspending the connection between the wireless device andthe wireless network; and transmit, to the wireless device via theinterface, a second message that indicates that the connection betweenthe wireless device and the wireless network is being resumed using thestored wireless device context of the wireless device.
 48. (canceled)49. (canceled)
 50. (canceled)
 51. (canceled)
 52. (canceled)
 53. Thewireless device of claim 20, wherein a Medium Access Control (MAC)control element associated with the third message comprises a copy of aportion of the second message that requests that the connection betweenthe wireless device and the wireless network be resumed.
 54. Thewireless device of claim 53, wherein the portion of the second messagecomprises the part of the resume identifier that identifies the wirelessdevice.
 55. The wireless device of claim 53, wherein the second messageis transmitted in an uplink common control channel service data unit,and the portion of the second message is provided by truncating theuplink common control channel service data unit.
 56. The wireless deviceof claim 53, wherein the second message is transmitted in an uplinkcommon control channel service data unit, and the portion of the secondmessage is provided by truncating the uplink common control channelservice data unit to a size of an existing content resolution identityMAC control element in LTE.
 57. The wireless device of claim 53, whereinthe second message is transmitted in an uplink common control channelservice data unit, and the portion of the second message is provided bytruncating the uplink common control channel service data unit to 48bits.
 58. The network node of claim 57, wherein a Medium Access Control(MAC) control element associated with the second message comprises acopy of a portion of the first message that requests that the connectionbetween the wireless device and the wireless network be resumed.
 59. Thenetwork node of claim 57, wherein the portion of the first messagecomprises the part of the resume identifier that identifies the wirelessdevice.
 60. The network node of claim 57, wherein the first message istransmitted in an uplink common control channel service data unit, andthe portion of the first message is provided by truncating the uplinkcommon control channel service data unit.
 61. The network node of claim57, wherein the first message is transmitted in an uplink common controlchannel service data unit, and the portion of the first message isprovided by truncating the uplink common control channel service dataunit to a size of an existing content resolution identity MAC controlelement in LTE.
 62. The network node of claim 57, wherein the firstmessage is transmitted in an uplink common control channel service dataunit, and the portion of the first message is provided by truncating theuplink common control channel service data unit to 48 bits.